Reader set encoding for directory of shared cache memory in multiprocessor system

ABSTRACT

In a parallel processing system with speculative execution, conflict checking occurs in a directory lookup of a cache memory that is shared by all processors. In each case, the same physical memory address will map to the same set of that cache, no matter which processor originated that access. The directory includes a dynamic reader set encoding, indicating what speculative threads have read a particular line. This reader set encoding is used in conflict checking. A bitset encoding is used to specify particular threads that have read the line.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is being filed concurrently with Ser. No. ______ [24692] Benefit is claimed of the following applications, in particular:

-   -   61/295,669, filed Jan. 15, 2010 and     -   61/299,911 filed Jan. 29, 2010,         both for “SPECULATION AND TRANSACTION IN A SYSTEM SPECULATION         AND TRANSACTION SUPPORT IN L2 L1 SUPPORT FOR         SPECULATION/TRANSACTIONS IN A2 PHYSICAL ALIASING FOR THREAD         LEVEL SPECULATION MULTIFUNCTIONING L2 CACHE CACHING MOST RECENT         DIRECTORY LOOK UP AND PARTIAL CACHE LINE SPECULATION SUPPORT”,

And of the following applications in general

Benefit of the following applications is claimed and they are also incorporated by reference: U.S. patent application Ser. No. 12/796,411 filed Jun. 8, 2010; U.S. patent application Ser. No. 12/696,780, filed Jan. 29, 2010; U.S. provisional patent application Ser. No. 61/293,611, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/684,367, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/684,172, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/684,190, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/684,496, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/684,429, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/697,799 filed Feb. 1, 2010; U.S. patent application Ser. No. 12/684,738, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/684,860, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/684,174, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/684,184, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/684,852, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/684,642, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/684,804, filed Jan. 8, 2010; U.S. provisional patent application Ser. No. 61/293,237, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/693,972, filed Jan. 26, 2010; U.S. patent application Ser. No. 12/688,747, filed Jan. 15, 2010; U.S. patent application Ser. No. 12/688,773, filed Jan. 15, 2010; U.S. patent application Ser. No. 12/684,776, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/696,825, filed Jan. 29, 2010; U.S. patent application Ser. No. 12/684,693, filed Jan. 8, 2010; U.S. provisional patent application Ser. No. 61/293,494, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/731,796, filed Mar. 25, 2010; U.S. patent application Ser. No. 12/696,746, filed Jan. 29, 2010; U.S. patent application Ser. No. 12/697,015 filed Jan. 29, 2010; U.S. patent application Ser. No. 12/727,967, filed Mar. 19, 2010; U.S. patent application Ser. No. 12/727,984, filed Mar. 19, 2010; U.S. patent application Ser. No. 12/697,043 filed Jan. 29, 2010; U.S. patent application Ser. No. 12/697,175, Jan. 29, 2010; U.S. patent application Ser. No. 12/684,287, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/684,630, filed Jan. 8, 2010; U.S. patent application Ser. No. 12/723,277 filed Mar. 12, 2010; U.S. patent application Ser. No. 12/696,764, filed Jan. 29, 2010; U.S. patent application Ser. No. 12/696,817 filed Jan. 29, 2010; U.S. patent application Ser. No. 12/697,164, filed Jan. 29, 2010; U.S. patent application Ser. No. 12/796,411, filed Jun. 8, 2010; and, U.S. patent application Ser. No. 12/796,389, filed Jun. 8, 2010.

All of the above applications are incorporated by reference.

GOVERNMENT CONTRACT

This invention was made with Government support under Contract No.: B554331 awarded by Department of Energy. The Government has certain rights in this invention.

BACKGROUND

The invention relates to conflict checking in a multiprocessor system with speculative execution.

A multiprocessor system typically includes cache memory. In the context of speculative execution, cache memory will normally include various data versions, i.e. versions that are created or read by threads of a program executing in parallel. These versions may be in conflict with one another. In other words, as threads execute out of order they may create or access data that is not.

In the case of the type of speculation called TM: when a thread reads data speculatively from a line, it sets its speculative reader bit in its local cache and the line is starting at that point in a “speculatively read, shared” state. If any thread now tries to write to the line, no matter to which point within the line, this write is broadcast to all caches. The standard coherence scheme without speculation would in this case invalidate all copies in all caches except for the local cache of the writer, and would mark the local version of the writer as modified. In TM, the transition from “speculatively read. shared” to invalid would cause the transaction for this core to fail and to be invalidated.

In the case of the type of speculation known as TLS, the most simple implementation behaves like TM described above. More evolved schemes compare the speculation IDs of the writer with the one used by the core that has the line in “speculatively read, shared” state. If the reader thread is older than the writer the reader is not invalidated and the line is not invalidated from its cache as well.

SUMMARY

The invention arose in the context of the IBM® Blue Gene® project where a cache memory is the point of coherence and conflict checking is done in control circuitry for that cache memory. More about these aspects of the project is to be found in the applications incorporated by reference. The present application relates to encoding read accesses in such control circuitry.

One embodiment is a method for use in a multiprocessor system. The system includes a plurality of processors running speculative threads in parallel; and at least one cache shared by the processors. The method includes maintaining a dynamic record of read accesses to the cache, directing accesses, and performing conflict checking using the record. The maintaining occurs in a control unit of the cache, maintaining a dynamic record of read accesses to the cache. The record includes, for each cache line, a format specification indication specifying a reader encoding format responsive to whether a read access has occurred and/or what type of read access has occurred. Memory accesses for a same physical address are directed through a same memory addressing scheme of the control unit from any of the processors. Conflict checking for all the processors of the system uses the record to locate potential conflicts.

Another embodiment is a multiprocessor system including a plurality of processors adapted to carry out speculative execution in parallel; at least one data pathway adapted to direct all memory accesses for a same physical address to a shared cache resource; and a cache memory. The cache memory including the shared cache resource and a directory based conflict checking mechanism. The mechanism includes a reader set encoding format that dynamically represents threads that have read from the shared resource and/or types of read accesses to the shared resource that have occurred.

Objects and advantages will be apparent in throughout this document and drawings.

BRIEF DESCRIPTION OF DRAWING

Embodiments will now be described by way of non-limiting example with reference to the following figures:

FIG. 1 shows an overview of a system within which the invention may be implemented.

FIG. 2 shows a map of a cache slice.

FIG. 3 is a schematic of the control unit of an L2 slice.

FIG. 3A shows a request queue and retaining data associated with a previous memory access request.

FIG. 3B shows interaction between the directory pipe and directory SRAM.

FIG. 3C shows structure of the directory SRAM 309.

FIG. 3D shows more about encoding for the reader set aspect of the directory.

DETAILED DESCRIPTION

A review of literature relating to reader set encodings follows. This literature review is not an admission that it would be obvious to combine the listed documents

-   -   “Bulk Disambiguation of Speculative Threads in Multiprocessors”,         Luis Ceze, James Tuck, Calin Cascaval, Josep Torrellas. ISCA,         June 2006. This paper describes a method of encoding reader and         writer sets. It stores all addresses accessed so far for reads         and writes in two sets (here called signatures) per thread. The         encoding is using a superset encoding using hashes. This set is         not stored in the cache directory.     -   Harris, T.; Cristal, A.; Unsal, O. S.; Ayguade, E.; Gagliardi,         F.; Smith, B.; Valero, M.; “Transactional Memory: An Overview,”         Micro, IEEE, vol. 27, no. 3, pp. 8-29, May-June 2007 In this         overview paper, an implementation is referenced in which the         directory of the first level cache stores only a single bit per         line to mark whether the line has been accessed speculatively:     -   J. Gregory Steffan. 2003. Hardware Support for Thread-Level         Speculation. Ph.D. Dissertation. Carnegie Mellon Univ.,         Pittsburgh, Pa., USA. AAI3159472. The implementation described         in this PhD these uses Epoch numbers per cache line, which are         equivalent to our speculation IDs. The theses just has a state         to indicate a line has been speculatively accessed, but it gives         no indication that it would store the Epoch number of the         readers. So it basically has only a single bit to signify a line         has been speculatively read and stores one such bit in the local         cache of the reading thread.     -   Jose Renau, James Tuck, Wei Liu, Luis Ceze, Karin Strauss, and         Josep Torrellas. 2005. Tasking with out-of-order spawn in TLS         chip multiprocessors: microarchitecture and compilation. In         Proceedings of the 19th annual international conference on         Supercomputing (ICS '05). ACM, New York, N.Y., USA, 179-188.         DOI=10.1145/1088149.1088173 Uses interval representation instead         of integer short IDs, allowing ID values between existing ID         values to be created later on. Still uses no ID ranges for         reader encoding, just a flag for a line being speculatively read         is assumed.

Throughout this disclosure a particular embodiment of a multi-processor system will be discussed. This discussion may include various numerical values or numbers of components. These values or numbers are not intended to be limiting, but only examples. One of ordinary skill in the art might devise other examples as a matter of design choice.

The present invention arose in the context of the IBM® BlueGene® project, which is further described in the applications incorporated by reference above. FIG. 1 is a schematic diagram of an overall architecture of a multiprocessor system in accordance with this project, and in which the invention may be implemented. At 101, there are a plurality of processors operating in parallel along with associated prefetch units and L1 caches. A plurality of threads execute in parallel on the processors. At 102, there is a switch. At 103, there are a plurality of L2 slices. At 104, there is a main memory unit. It is envisioned, for the preferred embodiment, that the L2 cache should be the point of coherence.

These threads can be the subject of “speculative execution,” meaning that a thread or threads can be started as a sort of wager or gamble, without knowledge of whether the thread can complete successfully. A given thread cannot complete successfully if some other thread modifies the data that the given thread is using in such a way as to invalidate the given thread's results. The terms “speculative,” “speculatively,” “execute,” and “execution” are terms of art in this context. These terms do not imply that any mental step or manual operation is occurring. All operations or steps described herein are to be understood as occurring in an automated fashion under control of computer hardware or software.

Three modes of speculative execution are to be supported: Speculative Execution (SE) (also referred to as Thread Level Speculation (“TLS”)), Transactional Memory (“TM”), and Rollback.

SE is used to parallelize programs that have been written as sequential program. When the programmer writes this sequential program, she may insert commands to delimit sections to be executed concurrently. The compiler can recognize these sections and attempt to run them speculatively in parallel, detecting and correcting violations of sequential semantics

When referring to threads in the context of Speculative Execution, the terms older/younger or earlier/later refer to their relative program order (not the time they actually run on the hardware).

In Speculative Execution, successive sections of sequential code are assigned to hardware threads to run simultaneously. Each thread has the illusion of performing its task in program order. It sees its own writes and writes that occurred earlier in the program. It does not see writes that take place later in program order even if (because of the concurrent execution) these writes have actually taken place earlier in time.

To sustain the illusion, the L2 gives threads private storage as needed, accessible by software thread ID. It lets threads read their own writes and writes from threads earlier in program order, but isolates their reads from threads later in program order. Thus, the L2 might have several different data values for a single address. Each occupies an L2 way, and the L2 directory records, in addition to the usual directory information, a history of which thread IDs are associated with reads and writes of a line. A speculative write is not to be written out to main memory.

One situation that will break the program-order illusion is if a thread earlier in program order writes to an address that a thread later in program order has already read. The later thread should have read that data, but did not. The solution is to kill the later software thread and invalidate all the lines it has written in L2, and to repeat this for all younger threads. On the other hand, without such interference a thread can complete successfully, and its writes can move to external main memory when the line is cast out or flushed.

Not all threads need to be speculative. The running thread earliest in program order can be non-speculative and run conventionally; in particular its writes can go to external main memory. The threads later in program order are speculative and are subject to be killed. When the non-speculative thread completes, the next-oldest thread can be committed and it then starts to run non-speculatively.

The following sections describe the implementation of the speculation model in the context of addressing.

When a sequential program is decomposed into speculative tasks, the memory subsystem needs to be able to associate all memory requests with the corresponding task. This is done by assigning a unique ID at the start of a speculative task to the thread executing the task and attaching the ID as tag to all its requests sent to the memory subsystem.

As the number of dynamic tasks can be very large, it may not be practical to guarantee uniqueness of IDs across the entire program run. It is sufficient to guarantee uniqueness for all IDs concurrently present in the memory system. More about the use of speculation ID's, including how they are allocated, committed, and invalidated, appears in the incorporated applications.

Transactions as defined for TM occur in response to a specific programmer request within a parallel program. Generally the programmer will put instructions in a program delimiting sections in which TM is desired. This may be done by marking the sections as requiring atomic execution. According to the PowerPC architecture: “An access is single-copy atomic, or simply “atomic”, if it is always performed in its entirety with no visible fragmentation.”

To enable a TM runtime system to use the TM supporting hardware, it needs to allocate a fraction of the hardware resources, particularly the speculation IDs that allow hardware to distinguish concurrently executed transactions, from the kernel (operating system), which acts as a manager of the hardware resources. The kernel configures the hardware to group IDs into sets called domains, configures each domain for its intended use, TLS, TM or Rollback, and assigns the domains to runtime system instances

At the start of each transaction, the runtime system executes a function that allocates an ID from its domain, and programs it into a register that starts marking memory access as to be treated as speculative, i.e., revocable if necessary.

When the transaction section ends, the program will make another call that ultimately signals the hardware to do conflict checking and reporting. Based on the outcome of the check, all speculative accesses of the preceding section can be made permanent or removed from the system.

The PowerPC architecture defines an instruction pair known as larx/stcx. This instruction type can be viewed as a special case of TM. The larx/stcx pair will delimit a memory access request to a single address and set up a program section that ends with a request to check whether the instruction pair accessed the memory location without interfering access from another thread. If an access interfered, the memory modifying component of the pair is nullified and the thread is notified of the conflict. More about a special implementation of larx/stcx instructions using reservation registers is to be found in co-pending application Ser. No. 12/697,799 filed Jan. 29, 2010, which is incorporated herein by reference. This special implementation uses an alternative approach to TM to implement these instructions. In any case, TM is a broader concept than larx/stcx. A TM section can delimit multiple loads and stores to multiple memory locations in any sequence, requesting a check on their success or failure and a reversal of their effects upon failure

Rollback occurs in response to “soft errors,”, temporary changes in state of a logic circuit. Normally these errors occur in response to cosmic rays or alpha particles from solder balls. The memory changes caused by a programs section executed speculatively in rollback mode can be reverted and the core can, after a register state restore, replay the failed section.

FIG. 2 shows a cache slice. It includes arrays of data storage 201, and a central control portion 202.

FIG. 3 shows features of an embodiment of the control section 102 of a cache slice.

Coherence tracking unit 301 issues invalidations, when necessary. These invalidations are issued centrally, while in the prior generation of the Blue Gene® project, invalidations were achieved by snooping.

The request queue 302 buffers incoming read and write requests. In this embodiment, it is 16 entries deep, though other request buffers might have more or less entries. The addresses of incoming requests are matched against all pending requests to determine ordering restrictions. The queue presents the requests to the directory pipeline 308 based on ordering requirements.

The write data buffer 303 stores data associated with write requests. This buffer passes the data to the eDRAM pipeline 305 in case of a write hit or after a write miss resolution.

The directory pipeline 308 accepts requests from the request queue 302, retrieves the corresponding directory set from the directory SRAM 309, matches and updates the tag information, writes the data back to the SRAM and signals the outcome of the request (hit, miss, conflict detected, etc.).

The L2 implements four eDRAM pipelines 305 that operate independently. They may be referred to as eDRAM bank 0 to eDRAM bank 3. The eDRAM pipeline controls the eDRAM access and the dataflow from and to this macro. If writing only subcomponents of a doubleword or for load-and-increment or store-add operations, it is responsible to schedule the necessary RMW cycles and provide the dataflow for insertion and increment.

The read return buffer 304 buffers read data from eDRAM or the memory controller 78 and is responsible for scheduling the data return using the switch 60. In this embodiment it has a 32 B wide data interface to the switch. It is used only as a staging buffer to compensate for backpressure from the switch. It is not serving as a cache.

The miss handler 307 takes over processing of misses determined by the directory. It provides the interface to the DRAM controller and implements a data buffer for write and read return data from the memory controller,

The reservation table 306 registers and invalidates reservation requests.

Per FIG. 3A, the L2 slice 72 includes a request queue 302. At 311, a cascade of modules tests whether pending memory access requests will require data associated with the address of a previous request, the address being stored at 313. These tests might look for memory mapped flags from the L1 or for some other identification. A result of the cascade 311 is used to create a control input at 314 for selection of the next queue entry for lookup at 315, which becomes an input for the directory look up module 312.

FIG. 3B shows more about the interaction between the directory pipe 308 and the directory SRAM 309. The vertical lines in the pipe represent time intervals during which data passes through a cascade of registers in the directory pipe. In a first time interval T1, a read is signaled to the directory SRAM. In a second time interval T2, data is read from the directory SRAM. In a third time interval, T3, a table lookup informs writes WR and WR DATA to the directory SRAM. In general, table lookup will govern the behavior of the directory SRAM to control cache accesses responsive to speculative execution. Only one table lookup is shown at T3, but more might be implemented.

FIG. 3C shows the formats of 4 directory SRAMs included at 309, to with:

-   -   a base directory 321;     -   a least recently used directory 322;     -   a COH/dirty directory 323 and 323′; and     -   a speculative reader directory 324.

In the base directory, 321, there are 15 bits that locate the line at 271. Then there is a seven bit speculative writer ID field 272 and a flag 273 that indicates whether the write is speculative. Then there is a two bit speculative read flag field 274 indicating whether to invoke the speculative reader directory 324, and a one bit “current” flag 275. The current flag 275 indicates whether the current line is assembled from all necessary versions to reflect the view of the ID stored in the writer ID field. The processor, A2, does not control the fields 272-275 directly. These fields are set by the L2 directory pipeline in response to speculative accesses.

If the speculative writer flag is checked, then the way has been written speculatively, not taken from main memory and the writer ID field will say what ID the write access was tagged with. If the flag is clear, the writer ID field is irrelevant.

The LRU directory indicates “age”, which is an ordering number reflecting the order of last use of the way. This directory is for allocating ways in accordance with the Least Recently Used algorithm.

The COH/dirty directory has two uses, and accordingly two possible formats. In the first format, 323, known as “COH,” there are 17 bits, one for each core of the system. This format indicates, when the writer flag is not set, whether the corresponding core has a copy of this line of the cache. In the second format, 323′, there are 16 bits. These bits indicate, if the writer flag is set in the base directory, which part of the line has been modified speculatively. The line has 128 bytes, but they are recorded at 323′ in groups of 8 bytes, so only 16 bits are used, one for each group of eight bytes.

Speculative reads are recorded for each way from which data is retrieved while processing a request. As multiple speculative reads from different IDs for different sections of the line need to be recorded, the L2 uses a dynamic encoding that provides a superset representation of the read accesses.

The speculative reader directory 324 has fields PF for the prefix determining the encoding type 281. An example of encoding type is shown including left boundary 282, right boundary 283, a first speculative ID 284, and a second ID 285. The speculative reader directory is invoked in response to flags in field 274.

FIG. 3D shows the possible formats of the reader set directory. The left column illustrates the seven possible formats of the reader set directory, while the right column indicates what the result in the cache line would be for that format. Formats 331, 336, and 337 can be used for TLS, while formats 331-336 can be used for TM.

Format 331 indicates that no speculative reading has occurred.

Format 332 uses two bit code “01” to indicate that a single seven bit ID, a, has read in a range delimited by boundaries denoted “left” and “right”.

If only a single TLS or TM ID has read the line, the L2 records the ID along with the left and right boundary of the line section so far accessed by the thread. Boundaries are always rounded to the next double word boundary.

If two IDs in TM have accessed the line, the IDs along with the gap between the two accessed regions are recorded. Format 333 uses two bit code “11” to indicate that a first seven bit ID denoted “α” has read from a boundary denoted with four bits symbolized by the word “left” to the end of the line; while a seven bit second ID, denoted “β” has read from the beginning of the line to a boundary denoted by four bits symbolized by the word “right.”

Format 334 uses three bit code “001” to indicate that three seven bit IDs, denoted “α,” “β,” and “γ,” have read the entire line. In fact, when the entire line is indicated in this figure, it might be that less than the entire line has been read, but the encoding has no space to store the additional information needed to characterize the footprint.

Format 335 uses five bit code “00001” to indicate that several IDs have read the entire line. The range of IDs is indicated by the three bit field denoted “ID up”. This range includes the sixteen IDs that share the same upper three bits. Which of the sixteen IDs have read the line is indicated by respective flags in the sixteen bit field denoted “ID set,” in other words all n for which: n/16=ID up and IDset(n mod 16)=1. For instance if IDup is 0, then ID 0 has read the line if IDset(0 mod 16)=IDset (0)=1, i.e., if the bit 0 of the 16 bit wide bitset is ‘1’. ID 1 is represented by bit 1, ID2 by bit 2 etc. If IDup is one, ID 16 is represented by bit 0, id 17 by bit 1 and so on.

An alternative encoding could use more bits than “ID up” to identify the set, e.g., by storing the value of the first ID. The set would then represent the IDs “first ID” to (“first ID”+width of bitset −1). The additional precision allows the set to start at any ID instead of at every 16^(th) ID. The “first ID” value serves here as a pointer to the set of ID represented.

If two or more TLS IDs have accessed the line, the youngest and the oldest ID along with the left and right boundary of the aggregation of all accesses are recorded.

Format 337 uses the two bit code “10” to indicate that two seven bit IDs, denoted “α” and “β” have read a range delimited by boundaries indicated by the four bit fields denoted “left” and “right.”

Format 336 uses the eight bit code “00010000” to indicate that groups of IDs have read the entire line. This group is defined by a 16 bit field denoted “IDgroupset,” i.e. all n for which: IDgroupset(n/8)=1. Each bit of this field represents a group of IDs, and the aggregate of all bits of this bitset represents the aggregate of all IDs. In the preferred implementation, a total of 128 IDs are implemented and the IDgroupset field is 16 bits wide. Each bit represents 8 subsequent IDs, resulting in all 128 IDs being represented by the 16 groups. When a bit in this bitset is set, the line has been read by at least one ID of the corresponding group.

When doing Write After Read (“WAR”) conflict checking, the formats of FIG. 3D are used. For each format 331-337, in the left column of FIG. 3D, the figure includes a corresponding block 331′-337′ in the right column that illustrates the extent of the line that was read by the read recorded by that format.

Rollback ID reads are not recorded.

If more than two TM IDs, a mix of TM and TLS IDs or TLS IDs from different domains have been recorded, the encodings shown do not provide field indicating the boundary of the accesses within a 128 B line. In this case, the two flags 274 indicate which of the two 64 B halves of the line have been speculatively accessed, increasing the resolution from 128 B to 64 B for the most common cases.

Although the embodiments of the present invention have been described in detail, it should be understood that various changes and substitutions can be made therein without departing from spirit and scope of the inventions as defined by the appended claims. Variations described for the present invention can be realized in any combination desirable for each particular application. Thus particular limitations, and/or embodiment enhancements described herein, which may have particular advantages to a particular application need not be used for all applications. Also, not all limitations need be implemented in methods, systems and/or apparatus including one or more concepts of the present invention.

It is noted that the foregoing has outlined some of the more pertinent objects and embodiments of the present invention. This invention may be used for many applications. Thus, although the description is made for particular arrangements and methods, the intent and concept of the invention is suitable and applicable to other arrangements and applications. It will be clear to those skilled in the art that modifications to the disclosed embodiments can be effected without departing from the spirit and scope of the invention. The described embodiments ought to be construed to be merely illustrative of some of the more prominent features and applications of the invention. Other beneficial results can be realized by applying the disclosed invention in a different manner or modifying the invention in ways known to those familiar with the art.

The word “comprising”, “comprise”, or “comprises” as used herein should not be viewed as excluding additional elements. The singular article “a” or “an” as used herein should not be viewed as excluding a plurality of elements. Unless the word “or” is expressly limited to mean only a single item exclusive from other items in reference to a list of at least two items, then the use of “or” in such a list is to be interpreted as including (a) any single item in the list, (b) all of the items in the list, or (c) any combination of the items in the list. Ordinal terms in the claims, such as “first” and “second” are used for distinguishing elements and do not necessarily imply order of operation.

Items illustrated as boxes in flowcharts herein might be implemented as software or hardware as a matter of design choice by the skilled artisan. Software might include sequential or parallel code, including objects and/or modules. Modules might be organized so that functions from more than one conceptual box are spread across more than one module or so that more than one conceptual box is incorporated in a single module. Data and computer program code illustrated as residing on a medium might in fact be distributed over several media, or vice versa, as a matter of design choice. Such media might be of any suitable type, such as magnetic, electronic, solid state, or optical

Any algorithms given herein can be implemented as computer program code and stored on a machine readable medium, to be performed on at least one processor. Alternatively, they may be implemented as hardware. They are not intended to be executed manually or mentally.

The use of variable names in describing operations in a computer does not preclude the use of other variable names for achieving the same function.

The present application may use language that is anthropomorphic in describing operations of a computer. Any such anthropomorphic language is not intended to imply that the claimed invention reads on a human being thinking or performing manual operations. The claims are intended to be interpreted as reading on operations of a machine. 

1. In a multiprocessor system comprising a plurality of processors running speculative threads in parallel; and at least one cache shared by the processors, a method comprising: in a control unit of the cache, maintaining a dynamic record of read accesses to the cache, the record comprising for each cache line a format specification indication specifying a reader encoding format responsive to whether a read access has occurred and/or what type of read access has occurred; directing memory accesses for a same physical address from any of the processors through a same memory addressing scheme of the control unit; and performing conflict checking for all the processors of the system using the record to locate potential conflicts.
 2. The method of claim 1, wherein the record comprises an identification of which speculative thread or threads has read a particular cache line.
 3. The method of claim 2, wherein the identification comprises at least one thread identification number.
 4. The method of claim 3, comprising an identification number for each of a plurality of threads that has read that version.
 5. The method of claim 2, wherein the identification comprises, for each version of data, an indication of a set of identification numbers that read that version.
 6. The method of claim 5, wherein the record comprises a bitset that encodes thread identification numbers of a group of threads.
 7. The method of claim 6, wherein the bitset encodes a subset of available thread identification numbers in accordance with one bit per number.
 8. The method of claim 7, wherein the subset is all thread identification numbers sharing a sequence of more significant bits.
 9. The method of claim 8, further comprising storing a pointer to locate speculation identification numbers associated with the subset.
 10. The method of claim 6, wherein the bitset is adapted to be able to indicate up to all available speculation identification numbers in accordance with one bit per group of IDs.
 11. The method of claim 5, wherein the record comprises two IDs defining the boundaries of a range of ordered IDs.
 12. The method of claim 2, wherein the identification is adapted to represent a superset of the threads that have accessed the line.
 13. The method of claim 1, wherein conflict checking comprises comparing to detect conflicts of current access with previous accesses.
 14. The method of claim 1, wherein conflict checking comprises invalidating copies of lines where requesting memory accesses have implicated multiple values.
 15. The method of claim 1, wherein the dynamic record comprises an indication of how many threads read the line.
 16. The method of claim 1, comprising recording read accesses to more than one version from a single read request.
 17. The method of claim 1, wherein maintaining comprises storing IDs in the directory to distinguish one or more speculative versions for the same address.
 18. The method of claim 1, wherein the reader encoding format is dependent on a mode of speculation used in generating the read access.
 19. The method of claim 1, wherein the reader encoding format is dependent on what set of identification numbers of threads have accessed the cache line.
 20. The method of claim 1, further comprising abrogating recordation of portions of lines read responsive to one or more of the following conditions: more than two speculative TM threads have read from the line; a mix of TM and TLS threads have read from the line; and TLS threads from different domains have read from the line.
 21. The method of claim 1, wherein the indication comprises a format allowing for one to three speculative thread identification numbers to be listed.
 22. A multiprocessor system, comprising a plurality of processors adapted to carry out speculative execution in parallel; at least one data pathway adapted to direct all memory accesses for a same physical address to a shared cache resource; a cache memory comprising the shared cache resource and a directory based conflict checking mechanism, the mechanism comprising a reader set encoding format that dynamically represents threads that have read from the shared resource and/or types of read accesses to the shared resource that have occurred.
 23. The system of claim 22, wherein the format comprises an indication of which speculative thread or threads has read a particular cache line.
 24. The system of claim 23, wherein the format comprises a bitset that encodes thread identification numbers of a group of threads.
 25. The system of claim 22, wherein the format is dependent on a mode of speculation used in generating a corresponding read access. 